BDMS 111: location updates & other#137
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is
|
jirhiker
reviewed
Sep 15, 2025
| @@ -28,7 +29,7 @@ class Group(Base, AutoBaseMixin, ReleaseMixin): | |||
| description: Mapped[str] = mapped_column(String(255), nullable=True) | |||
| name: Mapped[str] = mapped_column(String(100), nullable=False, unique=True) | |||
| project_area: Mapped[Optional[WKBElement]] = mapped_column( | |||
Member
There was a problem hiding this comment.
rename to region_of_interest (?)
jirhiker
approved these changes
Sep 15, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
This PR addresses the following problem / context:
productionandstaging)elevationneeded to be separated frompointfor a locationHow
Implementation summary - the following was changed / added / removed:
state,county, andquand_namefields using a location'spointx/y valuesLU_CoordinateAccuracy:Mis a key in the table as well asLU_SiteType:M)12:00:00 AMor00:00:00) the time doesn't change but the time zone is set to UTCNotes
Any special considerations, workarounds, or follow-up work to note?
namewas removed fromLocationuntil further consideration and debatetransfers/util.pyare applicable and used throughout the API, so they were moved toservices/util.pyfor repo-wide accessconstants.pyfor style